- 5 minutes to read

Release Notes

Configure Nodinite BizTalk Server Monitoring Agent

Unlock the full potential of your BizTalk Server environment with Nodinite. This guide empowers you to configure advanced monitoring and management for your BizTalk Server Group, ensuring reliability, visibility, and control.

Animation: the Configuration dialog of the BizTalk Server Monitoring Agent, with the BizTalk tab, the connection string and a new BizTalk Application filter
Open Configuration, check the connection string on the BizTalk tab, and add a RegEx to the BizTalk Application(s) filter. After Save and close, the agent stops monitoring the matching BizTalk Applications.

What You'll Achieve

The Monitoring Agent delivers a comprehensive suite of features to help you proactively receive alerts and perform Remote Actions, so you can resolve issues before they impact your business. Start with the essentials and expand your configuration as you discover more value—each feature is designed to make your integration landscape more robust and manageable.

🚀 Before leveraging monitoring and remote configuration, ensure you have installed and created the initial Monitoring Agent Configuration for the Nodinite Microsoft BizTalk Server Monitoring Agent. If you're new to Nodinite, start here.

Applications

All BizTalk Server artifacts are automatically registered as Resources. These are organized into Applications and Categories.

Note

Understanding Application Name Assignment

Nodinite uses two different patterns for Application Name assignment based on resource type:

System-Wide Resources (use BizTalk Group Name as Application Name):

  • Group — Overall environment health and metrics
  • Host Instances — Windows services serving all applications
  • Health Check — Environment-level monitoring (MessageBox, DTA, Spool, Tracking Data)
  • Tracking — System-wide tracking capabilities

BizTalk Application Resources (use actual BizTalk Application Name):

Why This Matters:

  • Uniqueness: System-wide resources need unique identification when monitoring multiple BizTalk environments (Dev, Test, Prod)
  • Filtering: You can create Monitor Views filtered by BizTalk Group Name to see all system resources, or by specific BizTalk Application Names to see application-specific artifacts
  • ApplicationId = int.MaxValue: System-wide resources use this internal identifier as a design pattern for virtual grouping

See the Group page for detailed explanation and examples.

Depending on your BizTalk Server edition, you may face application limits (e.g., Branch and Standard editions). To overcome these, the agent can create virtual Applications based on service names, such as Receive Ports and Send Ports, ensuring you never miss critical monitoring.
BizTalk Applications
Visualizing BizTalk Applications and their organization in Nodinite.

Remote Configuration of BizTalk Servers

As a Nodinite Administrator, click the 'Configuration' button to open a modal and configure the agent:
Remote Configuration
Click the 'Configuration' button to open a dialog for configuring the agent.

You can fine-tune configurations on each Resource using the Action button, provided the Monitor View has Remote Actions enabled.

Each part of the configuration has its own page:

Tab What you set Page
BizTalk The BizTalkMgmtDb connection string on SQL Server, Always On Availability Groups (AOAG) listeners, and RegEx filters for Applications and Resources BizTalk Tab
Health Check Six sub-tabs: Misc (orphaned DTA instances, reference counts, throttling), Assemblies & Files (the comparison across the BizTalk Servers in the Group), Spool, Tracking Data, SQL Agent Jobs, and SSO Health Check Tab
Instance thresholds Warning and error counts and time spans on six sub-tabs (Suspended, Active, Dehydrated orchestrations, Ready to run, Retrying, Scheduled), globally or per Application in Specific configurations Instances Tab
Tracking Warnings for pipeline tracking, and tracking configurations applied automatically to ports and orchestrations Tracking Tab
Settings Environment, debug, culture and CSV options, the Agent Database with auditing, and access to suspended message bodies Settings Tab

Tip

New to the agent? Start with the BizTalk Tab: nothing is monitored until the connection string is set. Then tune the Health Check Tab and Instances Tab thresholds as you learn what normal looks like in your environment.

Save

Click 'Save' or 'Save and close' to apply your changes. New settings are evaluated on the next synchronization.
Save and Close buttons
Save your configuration changes in Nodinite.

Note

The time to reflect new settings depends on the agent's synchronization interval. Click Sync Now for immediate updates.

Save and close – Save and exit.
Close – Exit without saving. The button reads Cancel while the dialog holds unsaved changes.

Important

A saved filter or threshold changes the state of the agent's Resources, and with it the alerts in every Monitor View that shows them. Try changes on a test environment first.

Add BizTalk Monitoring Agent Configuration

After installing the Microsoft BizTalk Server Monitoring Agent, provide Nodinite with connection details so the Monitoring Service can recognize your new agent.

No monitoring or configuration is possible until these steps are completed.

Configuration Steps

  1. Add and configure a new Monitoring Agent Configuration.

    Find connection info in the README.txt file in the installation folder.

  2. Use Remote Configuration to set up the agent (see the tabs above).
  3. Create self-service enabled Monitor Views for your business needs.
  4. Fine-tune Resources using Remote Actions.

Next Steps